Add "gpgkeypath" option to remotes
authorColin Walters <walters@verbum.org>
Wed, 16 Nov 2016 14:13:54 +0000 (09:13 -0500)
committerAtomic Bot <atomic-devel@projectatomic.io>
Thu, 17 Nov 2016 09:44:07 +0000 (09:44 +0000)
commitf244c702772c69378099685316033d4a6f7b862c
tree8dfb779a89ac016df89bde1848287cd635ee5a5e
parent3cd5e6b41a6730ff2624ab125b51e12601913712
Add "gpgkeypath" option to remotes

For Project Atomic, we already have RPM signatures which use files in
`/etc/pki/rpm-gpg`.  It's convenient to simply bind the OSTree remote
configuration to those file paths, rather than having duplicate key
data.

This does mean that we need to parse the files for verification, so we
end up importing them into the verifier's temporary keyring, which is
a bit ugly, but it's what other projects do.

Closes: https://github.com/ostreedev/ostree/issues/573
Closes: #575
Approved by: giuseppe
man/ostree.repo-config.xml
man/ostree.xml
src/libostree/ostree-gpg-verifier.c
src/libostree/ostree-gpg-verifier.h
src/libostree/ostree-repo.c
tests/test-remote-gpg-import.sh